Change description

in setClassification.deleteClassification flow, taskManagement.getInProgressTasks() is fetching tasks from gremlin query, which is inherently slow on large-dataset tenants. Instead of doing a gremlin query to fetch in-progress tasks, added an ES-fetching mechanism.

Alternative to current implementations which failed

Alternative was that, we simply remove the getInProgressTasks() check so that deleteClassification can detach and create deleteTasks while ADD-PROPAGATION was running. It provided an IllegalStateException issue [see below]

Along with causing inconsistencies [see below]

This is while the delete-propagation task found nothing to remove.^

Current implementation proof

Type of change

• Bug fix (fixes an issue)

Related issues

Fix #1

Checklists

Development

• Lint rules pass locally
• Application changes have been tested thoroughly
• Automated tests covering modified code pass

Security

• Security impact of change has been considered
• Code follows company security practices and guidelines

Code review

• Pull request has a descriptive title and context useful to a reviewer. Screenshots or screencasts are attached as necessary
• "Ready for review" label attached and reviewers assigned
• Changes have been reviewed by at least one other contributor
• Pull request linked to task tracker where applicable